Text objects represent text output to be displayed to the user and are associated with goal values. For example with this rule:
if errorMessage = "Code too long to load" then problem = srcbuf_too_small
There would be a text object named 'srcbufTooSmall' that explains the problem for the user:
id |
srcbuf_too_small |
path |
/ code |
type |
text |
text |
One of your predicates is too large to load. You can either increase 'srcbuf' in your .INI file, or break up the predicate into multiple predicates. |
Text field can contain the values of other facts or text fields. For example:
%header% We recommend you run %num_miles% today. %footer%
Assuming there are text objects named 'header' and 'footer', the KnowledgeWright reasoning engine will replace the names in percent signs with the text from those objects. Further, KnowledgeWright will determine the value of num_miles and replace it before displaying the text for the user. The value can come from a fact, question, sql query, rule or table.
The properties of text objects are:
| Property Name | Description | Default Value | Required |
| id | The name of this object. See Object Names for details. | <none> | yes |
| path | The folder this object is located in. See Folders for details. | / | yes |
| description | A text description (comment)--not used during reasoning. | <none> | no |
| type | Whether this text is presented here or read from a file. | text | yes |
| text | The text to be displayed. | yes | |
| file | The name of the file to be displayed, in which case it must reside in the same directory as the .kb file. Otherwise, it can be the full pathname of a file.. | yes |